<li><a href="#support.what2do">"Why can't I ...? Why won't ... work?" What
to do in case of problems</a></li>
<li><a href="#support.support">Whom do I contact for support?</a></li>
</ul>
<h3><a name="support.what2do" id="support.what2do">"Why can't I ...? Why won't ... work?" What to do in case of
problems</a></h3>
<p>If you are having trouble with your Apache server software, you should
take the following steps:</p>
<dl>
<dt>Check the ErrorLog!</dt>
<dd>Apache tries to be helpful when it encounters a problem. In many
cases, it will provide some details by writing one or more messages to the
server error log. Sometimes this is enough for you to diagnose & fix
the problem yourself (such as file permissions or the like). The default
location of the error log is
<code>/usr/local/apache2/logs/error_log</code>, but see the <code class="directive"><a href="../mod/core.html#errorlog">ErrorLog</a></code> directive in your config files for the
location on your server.</dd>
<dt>Check the ErrorLog again!</dt>
<dd>Nearly all problems can be solved by reading the error log.</dd>
<dt>Check the <a href="http://httpd.apache.org/docs/2.2/faq/">FAQ</a>!</dt>
<dd>The latest version of the Apache Frequently-Asked Questions list can
always be found at the main Apache web site.</dd>
<dt>Check the Apache bug database</dt>
<dd>Most problems that get reported to The Apache Group are recorded in
the <a href="http://httpd.apache.org/bug_report.html">bug database</a>.
<strong>Please</strong> check the existing reports, open
<strong>and</strong> closed, before adding one. If you find that your
issue has already been reported, please <em>don't</em> add a "me, too"
report. If the original report isn't closed yet, we suggest that you
check it periodically. You might also consider contacting the original
submitter, because there may be an email exchange going on about the
issue that isn't getting recorded in the database.</dd>
<dt><a id="support.what2do.user-support" name="support.what2do.user-support">Ask in a user support forum</a></dt>
<dd><p>Apache has an active community of users who are willing to share
their knowledge. Participating in this community is usually the best and
fastest way to get answers to your questions and problems.</p>
core_output_filter: writing data to the network</a></h3>
<p>Apache uses the <code>sendfile</code> syscall on platforms
where it is available in order to speed sending of responses.
Unfortunately, on some systems, Apache will detect the presence of
<code>sendfile</code> at compile-time, even when it does not work
properly. This happens most frequently when using network or
other non-standard file-system.</p>
<p>Symptoms of this problem include the above message in the error
log and zero-length responses to non-zero-sized files. The
problem generally occurs only for static files, since dynamic
content usually does not make use of <code>sendfile</code>.</p>
<p>To fix this problem, simply use the <code class="directive"><a href="../mod/core.html#enablesendfile">EnableSendfile</a></code> directive to disable
<code>sendfile</code> for all or part of your server. Also see
the <code class="directive"><a href="../mod/core.html#enablemmap">EnableMMAP</a></code>, which can
<code>error_log</code>, accompanied by a <code>Forbidden</code>
message to the client usually indicates a problem with your
filesystem permissions, rather than a problem in the Apache HTTP
Server configuration files. Check to make sure that the
<code class="directive"><a href="../mod/mpm_common.html#user">User</a></code> and <code class="directive"><a href="../mod/mpm_common.html#group">Group</a></code> running the child processes
has adequate permission to access the files in question. Also
check that the directory and all parent directories are at least
searchable for that user and group (i.e., <code>chmod
+x</code>).</p>
<p>Recent releases of Fedora Core and other Linux distributions
using SELinux have additional access restrictions beyond those
used by the basic filesystem. Violations of these restrictions
will also result in a <code>Permission denied</code> message. See
the <a href="http://fedora.redhat.com/docs/selinux-faq-fc3/">Fedora
SELinux FAQ</a> and <a href="http://fedora.redhat.com/docs/selinux-apache-fc3/">Apache
SELinux Policy Document</a>.</p>
</div></div>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="../en/faq/all_in_one.html" title="English"> en </a> |
<a href="../ja/faq/all_in_one.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
<a href="../ko/faq/all_in_one.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
</div><div id="footer">
<p class="apache">Copyright 1995-2006 The Apache Software Foundation or its licensors, as applicable.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
